System and Method for Maintaining Recipe Ratios when Measuring Ingredients for Culinary Combinations

ABSTRACT

A system and method for assisting a user in assembling a culinary combination according to a recipe. The system comprises a scale and a computing device configured to communicate with the scale. The system displays information regarding ingredients of the recipe and displays a progress of assembling the culinary combination based on the information from the scale. In some embodiments, a bar graph is displayed with a bar proportional to the measured amount of an ingredient of the recipe compared to a target amount for the ingredient. In some embodiments, the system displays a build column of one or more recipe blocks, representing actions or ingredients of the recipe. An active recipe block is displayed with a portion of the recipe block displayed in a different manner in proportion to the measured amount of an ingredient of the recipe compared to a target amount for the ingredient.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims the benefit of, and priority to, co-pending U.S. Non-Provisional application Ser. No. 13/918,984, filed 16 Jun. 2013, which in turn claims priority to U.S. Provisional Patent Application Serial No. U.S. Provisional Application No. 61/800,252 filed on 15 Mar. 2013, both incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to weight scales. More particularly, the present invention relates to interactive systems of weight scales and computing devices.

BACKGROUND

Recipes are commonly used to create culinary combinations of food or drink. As used herein, culinary combinations will include creations of mixology and of cooking. The foundations of all recipes are culinary ratios. A culinary ratio is a fixed proportion of one or more ingredients of a recipe relative to another. These ratios are fundamental to the crafts of cooking and mixology. Understanding that recipes are ratios allow one to consistently scale or adjust recipes and to fix a recipe if one makes a mistake and adds too much of a certain ingredient.

When preparing food or drinks, it is best to use weight rather than volume for measuring most ingredients. Properties of a culinary combination are more closely dependent on the ratio of the weights or masses of ingredients, than on their volumes. For a culinary combination to have the desired properties, the ratios of the masses or weights of the ingredients must be achieved. Volumetric measurements may be convenient approximations for weight, but it the weight or mass of the ingredients that is desired. Measuring by volume can introduce inaccuracies. The volume of a certain mass of a material can change based on environmental conditions such as temperature, pressure and humidity. Because of this, powder ingredients like flour are in particular more accurately measured by weight than by volume. The volumetric measurement of liquids has other sources of inaccuracy. The shape of the target container, the viewing angle of the user, and the surface tension of the liquid can easily cause a 20% variation when visually judging what is “full” for small amounts of liquid. Weighing ingredients is the most reliable and consistent form of measuring, and it is the preferred method when it comes to using culinary ratios.

The standard digital scale can measure in metric or imperial units (also referred to as the U.S. customary units or avoirdupois units). A scale measuring a liquid detects weight, but some are configured to report the amount detected in volume units such as milliliters or fluid ounces (defined as 1/16 of a pint or 1/128 of a gallon in the US customary units system). However, this assumes the liquid is water or has a similar volume/weight ratio (density) as water. Some liquids have densities that are different from water, which can throw off the accuracy of using a scale to determine volume. For example, one milliliter is one gram of water and 30 grams of water is approximately 1 fluid ounce. The specific gravity of water is 1.00 (specific gravity is the ratio of density of fluid in question to the density of water). The specific gravity of simple syrup is typically 1.33. If a recipe calls for a 1 fluid ounce of simple syrup, weighing out one ounce of simple syrup will be rather inaccurate unless the scale knows the specific gravity of the fluid it is weighing and calculates fluid ounces accordingly.

Using a scale to maintain ratios can be especially challenging for standard cocktail recipes, which typically specify volume measurements. As an example a classic margarita recipe calls for the following ingredients:

60 ml tequila (2 fluid oz.) 30 ml Cointreau (1 fluid oz.) 23 ml fresh Lime Juice ( 3/4 fluid oz.) The specific gravity for each ingredient is approximately:

Tequila (0.95) Cointreau (1.04) Lime Juice (1.4) To measure a correct ratio by weight, the specific gravity of each ingredient must be considered. A scale assuming the specific gravity of water to measure ingredients would yield:

60 grams tequila = 68.01 ml =  (2.3 fluid oz) 30 grams Contreau = 29.0 ml = (0.98 fluid oz) 23 grams fresh lime juice = 13.6 ml = (0.46 fluid oz) This would result in significantly different ratios of ingredients than the original recipe and would not taste the same. A correct measurement incorporating the specific gravity of each ingredient would measure the following:

57 grams Tequila = (2 fluid oz.) 31.2 grams Cointreau = (1 fluid oz.) 32.2 grams Lime Juice = ( 3/4 fluid oz.)

The standard digital kitchen scale typically has a “tare” button. This is used to subtract the current weight on the smart scale 102, setting the current measured weight to zero. Using this button allows the weight of a containing vessel (like a bowl or glass) to be eliminated when measuring an ingredient. Using this button sequentially to build a multi-step recipe allows each ingredient to be measured independently as it is added.

This is a useful system and minimizes the use of containers. However, it does not have any awareness of the ingredients being measured or specific actions of the recipe. What if you make a mistake reading a recipe? Let's say a recipe asks for 70 grams of grape juice and 100 grams of apple juice and the user puts them in backwards (70 grams of apple juice and 100 grams of grape juice). It can be difficult to fix this, especially in the context of the entire recipe, where the measured amount for each ingredient must now be precisely altered to maintain a proper ratio.

Another problem is scaling a recipe. Simple scaling is practicable in one's head when doubling (2×) or halving (½) the recipe. However, other scaling changes, like making 30% less, or 1.75 times more, become more complicated. The common digital kitchen scale offers no assistance here.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:

The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the invention and, together with the detailed description, serve to explain the principles and implementations of the invention.

FIG. 1 shows an embodiment of the culinary ratio system with a one-way data connection from the smart scale to the smart device.

FIG. 2 shows a button pad on the smart scale.

FIG. 3 shows an embodiment of the culinary ratio system with a two-way data connection from the smart scale to the smart device.

FIG. 4 shows a display on the smart scale.

FIG. 5 shows an embodiment of the culinary ratio system 100 that uses an audio jack connection between the smart scale and smart device.

FIG. 6 shows a basic margarita recipe in traditional recipe form as it would typically be presented in a recipe book.

FIG. 7 shows the same basic margarita recipe displayed by the culinary ratio system in an interactive form called a build column.

FIG. 8 shows how a recipe can be scaled with the culinary ratio system.

FIG. 9 shows how the build column changes when different measurement units are selected.

FIG. 10 shows the build column at the beginning of assembling a culinary combination.

FIG. 11 shows the build column of FIG. 10 in which the recipe has advanced to the next recipe block.

FIG. 12 illustrates how the build column shows progress of an ingredient being added and measured.

FIG. 13 shows a completed ingredient step.

FIG. 14 is a graphical representation of a dead-band that extends below and above the target amount.

FIG. 15 shows a graphical representation of an off-center dead-band.

FIG. 16 shows advancement to the next recipe block representing the next step in the recipe.

FIG. 17 shows an example of how the user can choose the active ingredient.

FIG. 18 shows how the culinary ratio is maintained by automatically tracking ingredient amounts that go beyond their dead-bands.

FIG. 19 shows the build column displaying an ingredient event.

FIG. 20 shows how a user can correct a mistaken ingredient event.

FIG. 21 shows an ingredient history table before edit and the ingredient history table after edit.

FIGS. 22 and 23 show the build column 112 displayed on a tablet computer.

DETAILED DESCRIPTION

Before beginning a detailed description of the subject invention, mention of the following is in order. When appropriate, like reference materials and characters are used to designate identical, corresponding, or similar components in different figures. The figures associated with this disclosure typically are not drawn with dimensional accuracy to scale, i.e., such drawings have been drafted with a focus on clarity of viewing and understanding rather than dimensional accuracy.

In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application and business related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.

Use of directional terms such as “upper,” “lower,” “above,” “below”, “in front of,” “behind,” etc. are intended to describe the positions and/or orientations of various components of the invention relative to one another as shown in the various Figures and are not intended to impose limitations on any position and/or orientation of any embodiment of the invention relative to any reference point external to the reference.

The culinary ratio system 100 represents a significant advance in technology assisted cooking and mixology. As shown in the embodiments of FIGS. 1-6, the culinary ratio system 100 has a smart scale 102, a smart device 104 (computing device) and a communication connection 105 there between. Examples of the smart device 104 include a personal computer and mobile device such as a tablet computer or a mobile phone. The communication connection 105 can be wired or wireless and may be one-way or two-way. A smart scale 102 using a two-way link with a smart device 104 provides even more functionality.

The culinary ratio system 100 has a software app on the smart device 104 which is configured to receive real-time information from the smart scale 102. The app has access to information regarding actions, ingredients, and target amounts involved in a recipe. The app presents a user with actions to be performed and ingredients to be added.

The app is configured to assist the user in maintaining the culinary ratios of a recipe. The app is configured to accept input so that a user can change the overall serving size for the recipe at any time and the target amounts of each ingredient are automatically re-calculated and displayed. If too much of one ingredient is added, the app detects this and helps the user maintain the proper ratios. The number of servings is recalculated and displayed along with new target amounts for all other ingredients.

The culinary ratio system 100 has one or more graphical displays to show the real-time amount for any ingredient being added and may also show which ingredients have been added, which are left to be added, which actions have been performed, and which have still to be performed. In the preferred embodiment, there is a scale display 108 that is part of the smart scale 102 and a smart device display 109 that is part of the smart device 104. Both may be used for displaying information about recipe ingredients. Other embodiments may use only one of these displays.

In the preferred embodiment, the smart scale 102 has a button pad 110 (see FIG. 2) that can provide additional information for the app. Button presses can be sent to the app and used to invoke functions like: Change units; Next ingredient; Go back; Pause/Resume; and Adjust Ratio. The smart device 104 is also configured to provide a way for the user to provide information or enter commands to the app, such as a mouse, a keyboard or touch screen functionality in the smart device display 109.

The scale display 108 (see FIG. 4) can display real-time information for each ingredient including: a current ingredient indicator 132 showing the name of current ingredient; a connection status indicator 134 showing the connection status with the smart device 104; a measurement progress indicator 136 (such as a bar graph) showing an amount of the current ingredient added proportional to its target amount; a target amount indicator 138 showing the target amount for the current ingredient; and a measured amount indicator 140 showing the measured amount of the current ingredient.

The smart scale 102 may have lights and audio that can be used to help inform the user when pouring/adding an ingredient. This may be easier for some users when pouring—it allows them to look at the smart scale 102 instead of a smart device display 109. For example, the color of an LED can slowly change from green to red as an ingredient is added and approaches its target amount. Audio prompts from the smart device can be played though the smart scale 102 to call out ingredients and progress. Timers can also be started for actions requiring timing. These timers can be displayed on either the smart device 104 or the smart scale 102. An optional microphone in the smart scale 102 or the smart device 104 can be used for voice prompts/commands like “Next”, “Start Timer”, etc.

One-Way Communications Connection

FIG. 1 shows an embodiment of the culinary ratio system 100 with a one-way data connection from the smart scale 102 to the smart device 104. This connection can be wired or wireless. Data transferred and functions enabled for this configuration include: Real-time scale data; Button events; and Container presence.

Real-time scale data. Since there is a way for the smart device 104 to receive real-time data from the smart scale 102 in this configuration, the app on the smart device 104 performs all the necessary tare operations and unit calculations. The scale display 108 may simply show a “connected” message or its own independent weight information.

Button events (FIG. 2). Button presses or capacitive sensor touches on button pad 110 of the smart scale 102 are detected and sent to the smart device 104 in real-time. Some possible button functions include: Unit Selection, Tare, Next, Back, Pause, Resume, and Serving Size.

Container presence. The presence of a container can be detected by the smart scale 102 either by weight or by means of a sensor and this information sent to the smart device 104.

Two-Way Communications Connection

FIG. 3 shows an embodiment of a culinary ratio system 100 with a smart scale 102 using two-way communication with a smart device 104. This connection can be wired or wireless. A two-way communications connection has more options for synchronization and culinary workflow enhancement. Data transferred and functions enabled for this configuration include: Real-time scale data; Button events; Container presence; Scale display; Measurement/Unit Synchronization; Audio; LEDs; Buttons; and Microphone.

Scale Display (FIG. 4). In embodiments with a two-way communications connection, the scale display 108 can be synchronized and controlled by the app. Possible information displayed includes: Name of the current ingredient; Target amount of current ingredient; Amount/weight needed for the current ingredient (not shown in example); Real-time progress of measurement (graphical and/or numeric); Measured amount of current ingredient; Connection status with Smart Device; Measurement Units; and Serving Size/Scaling factor.

Measurement/Unit Synchronization. Because the smart device 104 can send commands to the smart scale 102, either the smart scale 102 or the smart device 104 can perform actions like “tare”. These actions can be synchronized with the recipe. Units and measurements can be synchronized in real-time.

Audio. In some embodiments, the smart scale 102 has a speaker (not shown) for playing audio prompts and instructions. These commands may be generated by and played from the app. The audio connection between the smart scale 102 and the smart device 104 may be digital or analog.

LEDs. In some embodiments, the smart scale 102 has LEDs (not shown). The LEDs on the smart scale 102 can be controlled by the app for real-time feedback. This control can be any combination of the following: Blinking/Pulsing; Brightness; Color; and individual LED controlled separately.

Container presence. The presence of a container can be detected by the smart scale 102 either sensing the weight of the container or by using a different type of sensor. Information of the presence of the container may be sent to the app on the smart device 104.

Buttons (FIG. 2). Button presses or capacitive sensor touches on the button pad 110 can be detected and sent to the smart device 104 in real-time. These buttons can be used to control the app directly. Some possible button functions include: Unit Selection; Tare; Next; Back; Pause; Resume; Serving Size/Scale; Start/Stop Timer; and Adjust Ratio.

Microphone. In some embodiments, the smart scale 102 has a microphone (not shown) that can record voice commands from the user and send them to the app for processing. A microphone/speaker combination on the smart scale 102 can be used to accomplish hands-free voice links with another remote user (like a phone call) during cooking. The audio connection for the microphone to the smart device 104 can be analog or digital. Voice commands could include: “Pause”; “Resume”; “Next”; “Back”; and “Start Timer”.

Wired Connection Example: Audio Jack

FIG. 5 shows an embodiment of the culinary ratio system 100 that uses an audio jack connection and associated communication protocols instead of USB or other standard or custom protocols. As smart devices become more popular it is increasingly difficult to support wired peripheral devices. This is due to the proliferation of different connectors on devices. The only standardized connector across the vast majority of devices is the headphone/microphone port, more commonly called an audio jack 164. This is a four-connector audio jack 164 that has: Ground; Microphone In; Left Audio Out; and Right Audio Out.

The smart scale 102 sends real-time data as analog audio data on the microphone channel, as illustrated in FIG. 5. Software in the app filters and decodes the data. An audio backchannel sends simple commands and data back to the smart scale 102 using one of the audio channels. The other audio channel can be used to play audio through a speaker in the smart scale 102.

Using the Culinary Ratio System

To aid the user in following a recipe and measuring multiple ingredients the culinary ratio system 100 presents an organized view of tasks. Major functions of the culinary ratio system 100 include:

-   -   Display ingredients and actions in a logical order for recipe         assembly.     -   Display progress of recipe construction.     -   Display target containers and tools as needed in recipe         construction.     -   Help the user to maintain proper ratios during construction,         including how best to fix any errors.     -   Allow the user to easily scale and adjust the recipe.     -   Allow easy and accurate measurement units change/selection.     -   Allow for easy substitutions.

The culinary ratio system 100 displays ingredients and actions of a recipe in a logical and intuitive order. FIG. 6 shows a basic margarita recipe in traditional recipe form 114 as it would typically be presented in a recipe book. FIG. 7 shows the same basic margarita recipe displayed by the culinary ratio system 100 in an interactive form called a build column 112. The build column 112 clearly displays information such as serving size, actions, ingredients, containers, and recommended order of actions and ingredients to make the recipe. All of this information is easily seen with a simple visual scan of the build column 112. In the preferred embodiment, the build column 112 is displayed on the smart device display 109. For example, FIGS. 22 and 23 show the build column 112 displayed on a tablet computer 162. Other embodiments of the culinary ratio system 200 may display ingredients and actions of a recipe in formats other than the build column 112, using formats such as pie charts, wheels, inclines, ladders or the like.

FIG. 7 shows some of the build column 112 features. A serving size block 115 is displayed, typically at the bottom. A target serving size indicator 116 is displayed with the serving size block 115, displaying a target serving size of the recipe. The target serving size is initially the serving size called for by the recipe, but the culinary ratio system 100 allows the user to change target serving size. This target serving size can be in absolute units or relative units. When in absolute units, the target serving size is the amount per standard serving called for by the recipe. When in relative units, the target service size is a scaling factor, representing the number of standard servings. In some embodiments, the app allows the user to switch serving size mode between absolute and relative serving size units. In the preferred embodiment, the default is the relative serving size units.

The build column 112 has one or more recipe blocks 119, representing steps of the recipe. In the depicted embodiment, the build column 112 is shown as comprising recipe blocks 119 that are stacked vertically. However, in other embodiments, the recipe blocks 119 may be arranged in other ways, such as in a horizontal row or in montage. The recipe blocks may be of various types, including recipe action blocks 120 and recipe ingredient blocks 122. A recipe action block 120 is associated with an action step of the recipe. Information related to the associated action step is displayed with the recipe action block 120. Such information typically includes a text description of the action step. A recipe action block 120 can also include a timer icon 124 for an action that the recipe calls to be performed for a specific length of time, like baking, simmering, or mixing. The timer icon may be associated with a timer function of the app that can be set to play an audio alarm or send an email or text. The timer function may be invoked by the user or automatically by the app.

A recipe ingredient block 122 is associated with a step of adding one of the ingredients of the recipe. In some embodiments, each recipe ingredient block 122 has a size based on the target amount of the ingredient in the recipe. In some embodiments, each recipe ingredient block 122 has a small, medium, or large size based on the target amount of the ingredient relative to the other ingredients in the recipe. Optionally, the same size recipe block could be used for all ingredients and actions. As each recipe block becomes active, it could expand to a larger block with more information, and then shrink as the next recipe block is activated. An ingredient icon 129 can also be displayed with a recipe ingredient block 122 to indicate the ingredient's type like fruit juice, powder, or liquid, or to indicate a particular ingredient.

In the depicted embodiment, recipe construction is displayed from bottom to top. The first action in the build column 112 of FIG. 7 is setting a shaker on the smart scale 102. On the right, target container icons 118 for each build phase are placed in a chronological relationship with the build column 112.

FIG. 8 shows how a recipe can be scaled with the culinary ratio system. If the user selects the serving size block 115, a serving size pop-up 126 appears, allowing the user to change/edit the target serving size of the recipe, changing either the amount or scaling factor, depending on which serving size mode the app is running. After a new serving size is selected, the target amounts of the ingredients of the recipe are changed in real-time showing the new target amounts. Changing the target serving size can also cause the target containers to be changed to larger, smaller, or more containers.

Another way to scale a recipe with the culinary ratio system 100 is to edit the amount used by one ingredient. The user selects one of the ingredients and then selects the target amount for the ingredient, which will cause the app to bring up an amount editor. The user simply enters a new target amount for this ingredient. The app changes the scaling factor of the recipe accordingly to maintain the culinary ratios. Then the target amounts for the other ingredients in rest of the build column 112 are automatically updated according to the scaling factor.

One more way to adjust the scale of a recipe with the culinary ratio system 100 is simply to add a larger amount for one of the ingredients during assembly of the recipe. The app may automatically change the scaling factor of the recipe if the measured amount of an ingredient exceeds the target amount for the ingredient, or in some embodiments, an upper threshold set slightly above the target amount. The app changes the scaling factor of the recipe accordingly to maintain the culinary ratios.

FIG. 9 shows how the build column 112 changes when different measurement units are selected. A measurement unit selection icon 128 is displayed with the build column 112. In this case, the measurement units have changed from a volume unit (fluid ounces) to a weight unit (grams). The build column immediately updates the target amounts for all ingredients to grams. For liquid ingredients, the app uses specific gravity constants for each ingredient to calculate accurate target amounts.

FIG. 10 shows the beginning of assembling a culinary combination. A first recipe block 142 is active. The active status of a recipe block 119 may be shown with the recipe block 119 highlighted, enlarged, or in some other enhanced manner. In this case, the first recipe block 142 is enhanced by highlighting it with a special color. The first recipe block 142 is a recipe action block 120 representing the action of placing the first container on the smart scale 102. Before advancing to the next recipe block, any weight added to the smart scale 102 will be automatically zeroed (commonly called a “tare”) before measuring the next ingredient. The target container icon 118 can also be highlighted or animated or otherwise enhanced to indicate that it has been detected (see FIG. 11)

In FIG. 11, the app has advanced the recipe to the next recipe block. There are several options to trigger a recipe advance. These options can be user selectable. Some options include: Weight-based auto-advance; Audio command advance; Recipe Block selection; and Scale button navigation.

Weight-based auto-advance: This option applies to events that involve a measureable weight change. Some examples of events include:

-   -   Placing a target container on the smart scale 102: The culinary         ratio system 100 can wait for a measureable weight change         followed by a short period of inactivity. It then performs a         “tare” and advance to the next recipe block. The user can also         adjust the period of inactivity for weight-based auto-advance.     -   Removing a target container from the smart scale 102: For this         action the culinary ratio system 100 would look for weight to be         removed from the smart scale 102. An example for this is the 5th         recipe block in FIG. 10 where the shaker will need to be removed         for mixing/shaking. The automatic timer can start once the         shaker is removed from the smart scale 102.     -   The target amount of an ingredient has been measured: Once the         culinary ratio system 100 detects that the target amount has         been achieved, followed by a short period of inactivity, it then         performs a “tare” and advances to the next recipe block. The         user can also adjust the period of inactivity for weight-based         auto-advance.

Audio command advance: A microphone may be monitored for vocal commands. The microphone may be mounted in the smart scale 102, built into the smart device 104, or connected to the smart device 104 by some other means such as Bluetooth. Some examples of possible vocal commands are:

-   -   “Next”: advances to the next recipe block.     -   “Lime Juice”: advances to a specific recipe block.     -   “Back”: moves to the previous recipe block.     -   “Recalculate” or “Scale”: recalculates the overall scale of the         recipe using the current measured amount of an ingredient.     -   “Start Timer”: starts a timer.

Recipe block selection: The user can actively choose another recipe block by interacting directly with the smart device 104 using touch screens or pointing devices like mice.

Scale button navigation: Buttons or touch sensors on the smart scale 102 can be used to advance or navigate up and down the build column. These buttons could be labeled “Next” or “Previous” or simply have arrows.

FIG. 12 illustrates how the build column 112 shows progress of an ingredient being added and measured. To show progress of the ingredient being added, a portion 145 of the activated recipe block may be displayed in a different manner than a remainder of the activated recipe block, such as a different color. The portion 145 of the activated recipe block displayed differently may be proportional to a ratio of the measured amount of the ingredient being added compared to its target amount. For example, the second recipe block 144 labeled “Silver/Blanco Tequila” in FIG. 12 is the activated recipe block. The second recipe block 144 initially is completed filled with a first color (e.g. green) that indicates that it is the active recipe block. Once a minimum threshold weight increase is detected (this threshold can be set based on the ingredient or amount to be weighed; or adjusted by the user or recipe author), the proportional amount measured is displayed as a portion 145 of the second recipe block 144 in a second color (e.g. yellow) from the bottom of the second recipe block 144. As the measured amount increases, a fill-line between the first and second colored portions of the second recipe block 144 rises. This serves a very clear visual guide for the user. The current measured amount may also be displayed in the block. This numeric value reflects the current measured amount.

FIG. 13 shows a completed ingredient step. The second recipe block 144 labeled “Silver/Blanco Tequila” is filled completely. In the example, the fill color is changed to a third color (e.g. red) indicating “stop” to the user. At this point, the system can auto-advance or be advanced directly by the user to another recipe block.

When adding ingredients it may be too much to ask any human to add the perfect amount with double-digit accuracy. FIG. 14 is a graphical representation of a dead-band 146 that extends below and above the target amount. The dead-band has an upper threshold and a lower threshold. As the measured amount enters the dead-band, the app indicates to the user to stop pouring. As in FIG. 13, this is done by filling the entire activated recipe block with the third color. This dead-band may be a simple percentage of the target amount. However, the percentage could be framed with pre-defined minimums or maximums to make sure the measurement process is human friendly. The recipe and/or the user may also adjust the dead-band.

For ingredients that are added by pouring it can be helpful if the dead-band is off-center and to make it easier for the user to get close to the target amount. FIG. 15 shows a graphical representation of an off-center dead-band 148 that has a lower threshold that is more distant from the target amount than is the upper threshold. This lower threshold could even be adjusted based on the pour rate.

FIG. 16 shows advancement to the next recipe block 119 representing the next step in the recipe. The second recipe block 144 (“Silver/Blanco Tequila”) is shown as completed, as indicated by being completely filled with the third fill color (red, in these examples). A third recipe block 150 (“Cointreau”) is the activated recipe block, as indicated by the first fill color (green, in these examples). Possible methods for this advancement are discussed with FIG. 11.

The user can choose the active ingredient at any time. FIG. 17 shows an example of this. The user has selected a fourth recipe block 152 (“Lime Juice”) as the activated block. Lime Juice will now be added before the Cointreau.

FIG. 18 shows how the culinary ratio is maintained by automatically tracking ingredient amounts that go beyond their dead-bands. When this happens, the entire recipe is adjusted in real-time. As the active ingredient measurement increases above the upper threshold of its dead-band, the recipe scaling factor/serving size and the other ingredient target amounts are adjusted. Any previous complete recipe ingredient block 122 will display an adjustment gap 154 at the top of the recipe ingredient block 122 in a different color than the rest of the recipe ingredient block 122. The adjustment gap 154 represents an adjustment amount for that ingredient that is the difference between the new target amount and the old target amount. The adjustment gap 154 is a portion of the recipe ingredient block 122 that is proportional to the adjustment amount compared to the new target amount. The user can then choose to select previous recipe ingredient blocks 122 and add enough of the associated ingredient to reach the new target amount. In the example of FIG. 18, the user has added 1.20 oz. of Cointreau instead of the target amount of 1.0 oz. The app has adjusted the scaling factor of the recipe from 1.0 to 1.2 to compensate. This changes the target amounts of the other ingredients, including the target amount of the Tequila from 2.0 oz. to 2.4 oz. The second recipe block 144 (“tequila”) is now shown with an adjustment gap 154 in the first color (green) that indicates that it is the activated recipe block. The user can then add more of the associated ingredient (“tequila”) to top it off to the new target amount of 2.4 oz.

The culinary ratio system 100 keeps an ingredient history of ingredient events. An ingredient event is essentially any measured ingredient activity occurring out-of-order or between periods of inactivity. Each significant ingredient event is delineated graphically for the user. FIG. 19 shows such an event for the second recipe block 144 (“tequila”). Continuing the example of FIG. 18, after the target amount of the second recipe block 144 (“tequila”) was adjusted to 2.4 oz., the user made a second pour of tequila. This second tequila ingredient event is recorded in the ingredient history and shown as an ingredient event region 156 within the second recipe block 144 separated from the rest of the block by a horizontal line.

The ingredient history is particularly useful for correcting mistakes. If the user accidentally added “lime juice” while the second recipe block 144 (“tequila”) is active, this will be recorded as its own ingredient event. The user can correct this mistake by selecting the ingredient event region 156 related to the mistake and moving it to the fourth recipe block 152 (“Lime Juice”). This correction is shown in FIG. 20.

The ingredient history is tracked in an ingredient history table. FIG. 21 shows the ingredient history table before edit 158 and the ingredient history table after edit 160. Each entry has an ingredient and the measured amount for that event. The history starts with the first event and goes down chronologically. The third event lists the lime juice event as tequila. Once the user corrects this by dragging that amount to the fourth recipe block 152 (“Lime Juice”), the table shows the correction. The total amount for any ingredient is the sum of its history.

Those skilled in the art will recognize that numerous modifications and changes may be made to the preferred embodiment without departing from the scope of the claimed invention. It will, of course, be understood that modifications of the invention, in its various aspects, will be apparent to those skilled in the art, some being apparent only after study, others being matters of routine mechanical, chemical and electronic design. No single feature, function or property of the preferred embodiment is essential. Other embodiments are possible, their specific designs depending upon the particular application. As such, the scope of the invention should not be limited by the particular embodiments herein described but should be defined only by the appended claims and equivalents thereof. 

What is claimed is:
 1. A system for communicating non-audio information between devices, the system comprising: a computing device with an audio port, the audio port having at least four connectors, including a microphone-in connector, and two audio-out connectors; a peripheral device with an audio jack, the audio jack having at least four connectors, including a microphone-out connector, and two audio-in connectors; wherein the peripheral device is configured for transmitting a first set of non-audio information to the computing device via the microphone-out connector of the audio jack; and wherein the computing device is configured for receiving the first set of non-audio information from the peripheral device via the microphone-in connector of the audio port.
 2. The system of claim 1, wherein the computing device is configured for transmitting a second set of non-audio information to the peripheral device via one of the audio-out connectors of the audio port; and wherein the peripheral device is configured for receiving the second set of non-audio information from the computing device via the audio-in connector of the audio jack. 